home *** CD-ROM | disk | FTP | other *** search
- Path: soap.news.pipex.net!pipex!usenet
- From: m.hendry@dial.pipex.com (Mathew Hendry)
- Newsgroups: comp.sys.amiga.applications
- Subject: Re: UUencode
- Date: Tue, 6 Feb 96 17:28:01
- Organization: Private node.
- Distribution: world
- Message-ID: <19960206.455DA0.F5E5@an040.du.pipex.com>
- References: <4edic0$auv@kdcol.kdcol.com> <19960128.4183E0.B91B@ak102.du.pipex.com> <p3KrAjf.anderson4@delphi.com> <4f5g90$bc@rkadw1.ple.af.mil>
- NNTP-Posting-Host: an040.du.pipex.com
- X-Newsreader: TIN [AMIGA 1.3 950726BETA PL0]
-
- Durwood Thrasher (thrasher@rkami2.ple.af.mil) wrote:
- : I think it's a little more complicated than that. The format I have to use to
- : get uuencode to work is:
- :
- : uuencode <myfile >newfilename myfile
- :
- : (Note that myfile appears twice.)
-
- In that case, one instance of "myfile" is redundant. What exactly do each of
- the two instances _mean_?
-
- The correct format depends on what version of uuencode you are using. Some
- take input from stdin, some from a file specified as a command line argument.
- Some send output to stdout, some to a file specified as a command line
- argument.
-
- So, there are four possible combinations:
-
- uuencode <myfile >outfile (input from stdin, output to stdout)
- uuencode <myfile outfile (input from stdin, output to file)
- uuencode myfile >outfile (input from file, output to stdout)
- uuencode myfile outfile (input from file, output to file)
-
- The first method is, I think, the standard UNIX usage. It's certainly the most
- flexible, and makes the command useful when using pipes.
-
- I don't think I've ever seen the second method used (it's rather an odd way of
- going about things), but the last two are fairly common.
-
- -- Mat.
-